[DE]Momaw

31 minutes ago, Valravn88 said:

Would be nice to know why Xinput has been disabled/inoperable.

XBOX controllers and DirectX-Input compatible emulations of it should still work in Warframe if you set "Steam Input" to disabled and then restart Steam (we've noticed that Steam is a bit reluctant to let go while running)

Resetting abilities at the start of each round of the Circuit is not intended, we are working on a fix to address this

51 minutes ago, TeeMeunTsundere said:

Prime Detail on the chest is missing. And now the missing Prime Detail on the chest is now a part of her Default Prime Helmet and the Default Prime Helmet is missing its effect on her head
 

I'm sorry, your pictures do not make it very clear what you are asking for because you have significantly changed the appearance of the frame between them.

You're asking for the "scarf" part of the Prime Helmet to be part of the Prime Body instead? But that would cause horrendous clipping with the other Wisp helmets that have scarves built into them...

This isn't a bug, the status chance bonus is "per shot". Shotguns split their status chance per shot across their pellet count.  12% status chance per shot divided across 8 pellets gives you the displayed increase from 7.5% per pellet to 9% per pellet.

We don't see any crashes submitted by your account. Are you not seeing the crash handler come up?

After testing further, it seems what's happening is that the numbers displayed on the HUD are not displayed the same way.  For a host we would expect some pellets to hit for 1X, and others to hit for 21X, but for a client the game is taking the sum of all pellets and then displaying the average. So you are getting the benefits of Devastating Attrition but it's being presented in a way that obfuscates the numbers. Entered this bug into our database.

UPDATE: After heart-felt discussion with our weapon engineer, this probably isn't something we will be able to fix. In order to optimize the way the game sends damage events over the network, the client doesn't actually receive the damage of each individual pellet. As you can imagine with some weapons shooting 20 or 30 pellets multiple times per second, the network bandwidth would scale up very rapidly. While what you have now doesn't look exactly right visually, in terms of GAMEPLAY,...

We've just published a new updated controller config which should fix the issues noted with "sticky"  controls.

In case you are having issues with your controller through Steam, again just to reinforce what Glen mentioned earlier:

• 1) Close Steam completely by clicking on its Icon in the task bar and choosing "Exit Steam", and then restart it.  This is a required step to force it pull the latest update.
• 2) In your Steam Library, right click on Warframe.  Click on "Properties".  Then click on "Controller", and "Enable Steam Input"
• 3) Launch the game
• 4) After logging in, bring up the Steam Overlay and click on the [Controller] icon to bring up your controller setting.
• 5) At the top of the controller settings window under "Current Layout", choose "Official Layout for Warframe" to set the baseline
• 6) You can now make custom changes on top of the Off...

We tested this and see the buff working for clients.  Can you be more specific about the circumstances where you're not seeing this work?  Is this only in *specific* gameplay modes? Does it matter if there was a host migration? Is there some other equipped mod in your loadout that is creating a conflict?

17 hours ago, AJAL8000 said:

Still doesn't Work. Its not fixed.

We know about the buff icon not displaying correctly, but how are you testing that shows the damage itself not working?

(it is VERY easy to miss the target and lose the buff while they are getting pushed around by the Incarnon mode's impact)

Please try this if your launcher is having issues

What would you expect to happen in this scenario?  If 2 players in the same squad have Combat Discipline aura,  then, it is impossible to lose health from kills. You only gain health because negative 10 plus 20, equals positive 10.  That is why Arcane Avenger does not trigger: you haven't lost any health.

We are aware of an issue for some players where the Warframe Launcher is immediately crashing when you try to start it. This is most likely to affect players with computer names with extended Unicode characters, or people that have shut down the Launcher while it was in the middle of attempting to update a core file.

If you are experiencing issues where the Launcher refuses to start, regrettably some manual action may be required. If you are not confident with your ability to work with files on your computer, the safest route is to simply reinstall Warframe. If you are willing to be a little more technical, follow these steps:

• Find the Warframe Launcher’s files (these are examples, your specific location may be different depending where you choose to install the game)
  • Windows Standalone clients:  %localappdata%\Warframe\Downloaded\Public\Tools\CEF3_1\V7\
  • Steam clients: C:\Program Files (x86)\St...

4 minutes ago, DonPritty said:

Any info in why the Corufell doesn't charge combo anymore?

From the patch notes: "Fixed consecutive Heavy Attacks not resetting the Melee Combo multiplier."

5 minutes ago, VladYvhv said:

I think people complaining about it being a nerf are the ones using impact procs for the "convert impact procs to slash procs" mods. In that sense, it's a nerf.

The maximum number of stacks of Impact that a target can have does not influence the maximum number of stacks of Bleed that a target can have.  These are unrelated effects. If people are worried about the change to Impact somehow affecting [Internal Bleeding] and [Hemorrhage],  then they can stop worrying. :)

Thanks for calling back!  We're always super interested in crash reports, especially if they come with a WAR number to save time.

In your case, I was able to look up the crash you're referring to. Our telemetry suggests that your video driver is a very old version, so first advice would be to try updating your video driver from Intel's website:
https://www.intel.com/content/www/us/en/support/articles/000090440/graphics.html

We're curious if this resolves the problem for you! If it doesn't, we may need to investigate further to make sure the Shader Cache feature is compatible across as much hardware as possible.

20 minutes ago, WindigoTG said:

Such a kerfuffle in order to fix Steel Path Trophy, yet still no Steel Path Trophy. 

I've verified that the Steel Path trophy will complete correctly now for an account that logs completion for all the nodes.  In your particular case, you have not done The Lone Story on Steel Path.

1 hour ago, Roble_Viejo said:

Not working. 

I guess I will miss the Incarnon Adapters of this week.

From the patch notes:

"in order to unlock Duviri on The Steel Path now, you may need to replay and complete The Circuit (complete at least one stage) and Lone Story (complete all stages, including defeating the Orowyrm) on their normal difficulty"

Should work fine if you do this.

10 hours ago, ---Magnus--- said:

They tried fixing a bug where some players cannot access Duviri SP content by locking everyone out of Duviri SP content. I Just did a single round of circuit and it's still not unlocking. Don't tell me I have to complete 10 stages of Circuit just to access the SP mode. I will literally uninstall this game.

From the update notes:  "In order to unlock Duviri on The Steel Path now, you may need to replay and complete The Circuit (complete at least one stage) and Lone Story (complete all stages, including defeating the Orowyrm) on their normal difficulty".  You didn't replay The Lone Story, that's what is holding you back.

7 hours ago, The_Android said:

For me this required playing the full experience, the story only, and then unlocking ALL tiers of the ...

This is not a bug. The Hata-Satya bonus is intended to reset when changing modes. You argue that it's technically not a "reload",  but our stance is that the spirit of the augment is you lose the accumulated buff when your active ammo is refilled: Which switching to and from Incarnon mode does.

After digging, we suspect the issue was due to a misconfiguration in the network itself and nothing to do with Warframe. After adjustments, we hope that the login issue is now resolved for Europe/North Africa that were hitting the affected part of the network.

If you're still experiencing problems and you know for a fact that you've using the right login details, we absolutely need your log file to continue diagnosis, so please open a ticket and attach the logs.